Skip to content

+tck #232 explain which tests are mendatory to be "compliant" #245

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

ktoso
Copy link
Contributor

@ktoso ktoso commented Mar 19, 2015

Resolves #232

@ktoso ktoso force-pushed the wip-readme-about-which-tests-to-impl-ktoso branch from 3760e19 to ced02c5 Compare March 19, 2015 00:48
@@ -479,6 +479,22 @@ public class SkippingIdentityProcessorTest extends IdentityProcessorVerification
}
```

## Which verifications must be implemented by an compliant implementation?
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Open for better suggestions for the section title here, ideas?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/an/a

@@ -479,6 +479,22 @@ public class SkippingIdentityProcessorTest extends IdentityProcessorVerification
}
```

## Which verifications must be implemented by an compliant implementation?
In order to be considered an Reactive Streams compliant we require implementations to cover their
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sentence is unclear. What does it mean? s/an/a

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm trying to answer the question @purplefox had here, paraphrasing it: "which tests do I need to implement / pass for my framework to be OK to say we're a reactive streams impl?" Since we have a TCK, I hoped to clarify which tests we want people to implement and pass here.

Do you think the "compliant" word is confusing or a good one here?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can it be made even simpler? Something like: In order to be a Reactive Streams implementation, aside from following the specification, one must also make sure that the implementations of the Publisher and Subscriber pass the TCK?

@ktoso ktoso force-pushed the wip-readme-about-which-tests-to-impl-ktoso branch from ced02c5 to 07ea4a1 Compare March 23, 2015 08:21
@@ -479,6 +487,22 @@ public class SkippingIdentityProcessorTest extends IdentityProcessorVerification
}
```

## Which verifications must be implemented by a compliant implementation?
In order to be considered an Reactive Streams compliant require implementations to cover their
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sentence does not make sense to me, is there some word missing?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was missing word (reactive streams compliant implementation), but that leads to repetition.
So I'll go with In order to be considered Reactive Streams compliant, implementations must cover their...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@viktorklang
Copy link
Contributor

👍 from me after addressing the last comment.
I'll open an issue on updating the conversational style to be neutral instead of using "we" and "you" etc.

@viktorklang
Copy link
Contributor

@reactive-streams/contributors Given that this only clarifies the TCK documentation and has already been available for review for 4 days, I'm going to merge this within 24h unless someone yells "no!". Thanks.

@viktorklang
Copy link
Contributor

@reactive-streams/contributors Merging without objection

@viktorklang
Copy link
Contributor

@ktoso this needs a rebase before it can merge cleanly. Would you mind?

@ktoso ktoso force-pushed the wip-readme-about-which-tests-to-impl-ktoso branch from 07ea4a1 to d503210 Compare March 27, 2015 11:25
@ktoso
Copy link
Contributor Author

ktoso commented Mar 27, 2015

@viktorklang rebased and pushed

@viktorklang
Copy link
Contributor

Thanks @ktoso, I'll merge once Travis approves

viktorklang added a commit that referenced this pull request Mar 27, 2015
…pl-ktoso

+tck #232 explain which tests are mendatory to be "compliant"
@viktorklang viktorklang merged commit bf67875 into reactive-streams:master Mar 27, 2015
@viktorklang viktorklang deleted the wip-readme-about-which-tests-to-impl-ktoso branch March 27, 2015 11:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clarification on which TCK tests are mandatory
2 participants